tbot Helm Chart: Add ability to configure securityContext#51817
Merged
strideynet merged 2 commits intomasterfrom Feb 5, 2025
Merged
tbot Helm Chart: Add ability to configure securityContext#51817strideynet merged 2 commits intomasterfrom
tbot Helm Chart: Add ability to configure securityContext#51817strideynet merged 2 commits intomasterfrom
Conversation
strideynet
temporarily deployed
to
docs-amplify
GitHub Actions
Inactive
github-actions
Bot
requested review from
hugoShaka,
marcoandredinis,
mmcallister,
ptgott,
r0mant,
tigrato,
xinding33 and
zmb3
Contributor
|
Amplify deployment status
|
strideynet
temporarily deployed
to
docs-amplify
GitHub Actions
Inactive
tigrato
approved these changes
Feb 4, 2025
marcoandredinis
approved these changes
Feb 4, 2025
public-teleport-github-review-bot
Bot
removed request for
hugoShaka,
mmcallister,
ptgott,
r0mant,
xinding33 and
zmb3
Contributor
|
@strideynet I'm 100% for defaulting to unprivileged in v18. Do you want to do it in this PR or in a followup? Also, would you mind trying to deploy tbot in a restricted PSS namespace and see if it works by default with your change? |
Contributor
Author
Plan was to pursue this in v18 - so in a seperate PR so this one can be backported. In that follow up PR, we can also include testing/evidence that tbot functions correctly. |
|
@strideynet See the table below for backport results.
|
strideynet
added a commit
that referenced
this pull request
Feb 6, 2025
* Add ability to configure securityContext of tbot pods * Newline at end of file
strideynet
added a commit
that referenced
this pull request
Feb 6, 2025
* Add ability to configure securityContext of tbot pods * Newline at end of file
This was referenced Feb 6, 2025
carloscastrojumo
pushed a commit
to carloscastrojumo/teleport
that referenced
this pull request
Feb 19, 2025
…ional#51817) * Add ability to configure securityContext of tbot pods * Newline at end of file
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default, we will continue to use an empty securityContext as I don't want to make a breaking change here. Perhaps we make a breaking change in v18 at a later date to introduce a securityContext by default that is compatible with the restricted PSS.
changelog: Added
securityContextvalue to thetbotHelm chart.